Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Schema.org JSON-LD Microdata for SEO (Homepage) #290

Merged
merged 13 commits into from
Dec 4, 2019

Conversation

RiccardoMasutti
Copy link
Contributor

We should add schema.org microdata to Bisq website for a better Search Engine Optimization as specified on https://schema.org/SoftwareApplication and https://developers.google.com/search/docs/data-types/software-app?hl=en.

Example of a Rich Snippet inside Google's SERP (search engine result page):
Google Rich Snippet

What is Microdata?

Microdata (like RDFa and Microformats) is a form of semantic mark-up designed to describe elements on a web page e.g. review, person, event etc. This mark-up can be combined with typical HTML properties to dedlfine each item type through the use of associated attributes. For example, ‘Person’ has the properties name, url and title – attributes can be applied to HTML tags to describe each property.

What is Schema.org?

Schema.org is a universally supported vocabulary extension by Google, Microsoft and Yahoo! for mark-up languages such as Microdata. It is designed to make the lives of webmasters easier, by offering one standardised mark-up understood by all the major search engines. Currently, Schema.org is compatible with Microdata, RDFa and JSON-LD.

What is JSON-LD?

Based on the popular JSON format, the linked data format JSON-LD allows webmasters to define the context of the data contained through the use of types and properties. When combined with Schema.org, these properties follow a standardised mark-up supported by major search engines, and joins Microdata & RDFa as methods for integration. Unlike Microdata & RDFa, JSON-LD offers greater ease of implementation with all the necessary mark-up contained within inline <script> tags, instead of wrapping HTML properties. However, as elegant and lightweight that JSON-LD is, there are some potential road blocks. In some instances it’s just not practical to mark-up content, for example that on a larger scale, as the content would need to be effectively repeated within the script tags in order to validate. Also as the mark-up is invisible, the likelihood of marking up content that is not on the visible page increases, which is against search engine usage guidelines. It is for these reasons that Google in particular still favours Microdata & RDFa for marking up HTML content.

Why use markups on Bisq website?

Marking up content on Bisq website can:

  • Lead to the generation of rich snippets in search engine results like the one showed on top
  • Enhance CTR (Click Through Rate) from the search result
  • Provide greater information to search engines to improve their understanding of the content on Bisq website

Read more about the importance of Rich Snippets: https://yoast.com/what-are-rich-snippets/

@RiccardoMasutti RiccardoMasutti changed the title Add Schema.org JSON-LD Microdata for SEO Add Schema.org JSON-LD Microdata for SEO (Homepage) Nov 21, 2019
Copy link
Contributor

@m52go m52go left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this—seems like low-hanging fruit to improve site traffic and perhaps downloads.

Some of my comments might be subjective, but I would say that such unclear things are better left unspecified/omitted.

_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Show resolved Hide resolved
_layouts/default.html Show resolved Hide resolved
_layouts/default.html Show resolved Hide resolved
@RiccardoMasutti
Copy link
Contributor Author

Thanks for this—seems like low-hanging fruit to improve site traffic and perhaps downloads.

Some of my comments might be subjective, but I would say that such unclear things are better left unspecified/omitted.

Structured data produces huge returns in terms of visits, CTR and SEO impact.
Please read Four excellent case studies of structured data for SEO

Copy link
Contributor

@m52go m52go left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RiccardoMasutti some final feedback. Mostly little things, along with a couple of questions that could use your advice/guidance.

_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Show resolved Hide resolved
_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Outdated Show resolved Hide resolved
_layouts/default.html Outdated Show resolved Hide resolved
RiccardoMasutti and others added 6 commits December 3, 2019 09:48
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Copy link
Contributor

@m52go m52go left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, one more thing. I just realized when merging #307 that this PR would cause post pages to have 2 conflicting JSON-LD specifications since post pages also use the default.html layout.

My suggested changes here skip adding JSON-LD markup to default.html when the page is for a post. This should fix the issue.

It looks to me like the changes in this PR should not conflict with the FAQ markup from #291, but let me know if you think otherwise.

_layouts/default.html Show resolved Hide resolved
_layouts/default.html Show resolved Hide resolved
RiccardoMasutti and others added 2 commits December 4, 2019 09:32
Co-Authored-By: Steve Jain <mfiver@gmail.com>
Co-Authored-By: Steve Jain <mfiver@gmail.com>
@m52go
Copy link
Contributor

m52go commented Dec 4, 2019

ACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants